home *** CD-ROM | disk | FTP | other *** search
- Path: comma.rhein.de!serpens!not-for-mail
- From: mlelstv@serpens.rhein.de (Michael van Elst)
- Newsgroups: comp.sys.amiga.misc
- Subject: Re: Speed: 68040 vs. 68060
- Date: 26 Feb 1996 18:54:07 +0100
- Organization: dis-
- Message-ID: <4gss3v$atg@serpens.rhein.de>
- References: <4foi00$60t@gondor.sdsu.edu> <3125E74D.3390@gih.no> <19960223.425E10.10CBD@an100.du.pipex.com> <19960225.7AF9790.E534@asd10-22.dial.xs4all.nl> <19960226.477570.1832@an174.du.pipex.com> <4grotj$8q3@serpens.rhein.de> <19960226.7B42F98.E8D9@asd06-03.dial.xs4all.nl>
- NNTP-Posting-Host: serpens.rhein.de
-
- jtv@xs4all.nl (Jeroen T. Vermeulen) writes:
-
- >Whether emulation code is inlined or not, there is a lot of overhead involved
- >simply in computing the expected results in software.
-
- Not really. For most operations the emulation (i.e. servicing a trap
- and interpreting an instruction) is the major part. Inline code is most
- often faster than a 68882 at same clockspeed.
-
- >AFAIK gcc inlines the emulation code for unimplemented instructions
-
- It doesn't.
-
- --
- Michael van Elst
-
- Internet: mlelstv@serpens.rhein.de
- "A potential Snark may lurk in every tree."
-